Introduction to Infrastructure as Code by Sneh Pandya & Riya Guha Thakurta

Author:Sneh Pandya & Riya Guha Thakurta
Language: eng
Format: epub
ISBN: 9781484286890
Publisher: Apress

The Way Ahead

Each deployment strategy is useful and has an architecture that is comparable to the others, but each has its own unique set of characteristics.

If you have the capability to run two fully functional infrastructure environments and your infrastructure does not change in a manner that is backward incompatible very often, a blue-green deployment strategy can provide you with the greatest number of secondary benefits while requiring the fewest number of changes to your applications. In the event that performance concerns arise or a catastrophe has to be recovered, it offers an environment with minimal downtime.

Canary deployment is an option worth considering if your application is both configuration-driven and modular, as well as if you have a limited amount of additional resources at your disposal. Because you do not have an additional environment that may be used for other matters, your operating and maintenance expenditures are reduced. Functionalities may be engaged or deactivated at whim and according to any number of criteria when utilizing a canary deployment, which is an extra advantage of employing this kind of deployment.

However, prior to using any approach, you will need to do a significant amount of planning and research into the architecture of your applications and environments.

It’s possible that even if you follow all of the best practices, something will slip through the strategy. Therefore, it is just as important to monitor for problems that develop after a deployment as it is to design and execute a faultless deployment.

Your team may benefit from using an application performance monitoring (APM) solution to monitor critical performance indicators such as server response times after the deployment of new software. The performance of an application may be significantly impacted by changes to the system architecture or the program itself. It’s also necessary to have an error monitoring system. It will quickly notify your team of any new or reactivated defects from a deployment that may disclose serious issues that need immediate correction.

It’s possible that the issues wouldn’t have been discovered without the use of an error tracking application. Only a small percentage of those who are aware of problems will go out of their way to report them. Long-term dissatisfaction or even a halt in present economic activities might result from poor customer service.

Developers and operations/DevOps teams may collaborate on post-deployment issues thanks to an error monitoring system. It’s possible that performance will suffer if the application and the architecture’s other services interact with one another. Inefficiency may be caused by a variety of factors, including problems with database queries, failed service connections, and a lack of resources. Checking in with the metrics and logs provided by the platform is something you need to do if the teams want to monitor the performance of the services provided by your architecture. The teams can be more collaborative and responsive because of this shared understanding.

In the next chapter, you will learn about the different aspects of businesses with respect to IaC as well as approaches, perspectives, and ways to develop, manage, and deploy IaC for various business solutions.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.